The function only retrieves the first 100 workflow runs (per_page=100) and doesn't handle pagination. If a repository has more than 100 workflow runs, some will not be cleaned up. Consider adding pagination logic to iterate through all pages, or document this limitation in the function's documentation.

Using created_at from the update workflow run to find subsequent CI/CD runs may be imprecise. Since the Update AL-Go System Files workflow runs with -wait (line 117), it completes before returning. The CI/CD workflow is triggered by the push event when the update workflow completes, so comparing against the update workflow's created_at (when it started) rather than when it completed could cause issues if multiple workflows run concurrently. Consider using $updateRun.updated_at or adding a small time buffer to ensure we capture the CI/CD run triggered by the update workflow's completion.

The logic for logging filtered scenarios may show incorrect results. The condition $filteredScenarios -notcontains $_.scenario will match all disabled scenarios from the config that are not in the final filtered list, but this includes disabled scenarios that were never in the list to begin with (e.g., if they didn't match the scenariosFilter). To accurately show only the scenarios that were actually filtered out, you should capture the pre-filter list and check: ($scenariosBeforeDisabledFilter -contains $_.scenario) -and ($filteredScenarios -notcontains $_.scenario)

The comment references "tmp repo" but the repository has been renamed to "e2e-bingmaps.appsource". This should be updated to reflect the new naming.

The code doesn't handle the case where the disabled-scenarios.json file doesn't exist. If the file is missing, the Get-Content command will throw an error and fail the workflow. Consider adding error handling or a check for file existence, or document that the file must always exist (even if empty as []).

The fallback logic uses Select-Object -First 1 on all workflow runs without filtering by event type. This could select a workflow run that's not a push event (e.g., a workflow_dispatch event), which wouldn't be the CI/CD run triggered by the Update AL-Go System Files workflow. Consider filtering by event type in the fallback: $run = $runs.workflow_runs | Where-Object { $_.event -eq 'push' } | Select-Object -First 1

Using gh api directly instead of invoke-gh is inconsistent with the rest of the codebase. The invoke-gh wrapper provides consistent error handling and authentication setup. This direct call should be replaced with invoke-gh wrapped in a try-catch block to handle the case where the repository doesn't exist.

The $LASTEXITCODE checks after invoke-gh and invoke-git calls are unnecessary and incorrect. These wrapper functions use cmdDo, which throws an exception when a command returns a non-zero exit code (see Actions/Github-Helper.psm1 line 296-298). The exit code checks will never be reached because an exception will be thrown first. These checks can be removed, as the try-catch block will handle errors.